SG-SST software in Colombia: choosing it for your company’s size, risks and operations
Choosing SG-SST software in Colombia starts with understanding how the company operates. Workforce size matters, alongside its activity, risk classification, sites, contracting arrangements and the capacity of its safety team. A long module list has limited value unless it explains who will perform each task and what information they need.
Colombia’s Decree 1072 of 2015 sets the management system framework, while Resolution 0312 of 2019 differentiates minimum standards according to company circumstances. Software should support the applicable requirements. Purchasing a system does not, by itself, demonstrate that those requirements have been met.
Describe the operation before reviewing screens
Prepare a scope statement covering the employing entity, locations, activities, workforce and employment or engagement arrangements. Add priority hazards and the workflows where information gets lost: inspections, training, actions, contractors or annual planning. Identify who maintains the records and who can make resource decisions.
The Explora entry on the OSH management system places each requirement within the management cycle. Then distinguish what is essential at launch from later improvements. A small business carrying out higher-risk activities may need rigorous operational controls despite having few administrative users.
Turn obligations into questions you can test
Avoid a generic checkbox stating “complies with Colombian regulations”. Ask the supplier to show the relationship between requirements, owners, activities and evidence. When an applicable obligation changes, the organisation needs to know who interprets it, who updates the workflow and how implementation is checked.
- Can preparation, approval and follow-up responsibilities be separated?
- How is an annual plan activity recorded and connected to an objective?
- What happens when an action becomes overdue or evidence is rejected?
- How are earlier assessment and document versions preserved?
- Who can access each information category, and how are permissions reviewed?
These are evaluation criteria for any proposal. Verify the answers against the offered scope and a practical demonstration instead of assuming that every application behaves in the same way.
Three scenarios for a useful demonstration
First, enter a hazard associated with a realistic task, arrange its technical assessment and link a preventive action. Follow the process through implementation and verification. The Explora entry on risk matrices helps distinguish the initial record from ongoing control monitoring.
Second, introduce a contractor that changes part of its workforce during the assignment. Check how the people involved, preventive information and required checks are updated. Third, generate an annual plan report showing completed, outstanding and amended activities, keeping the reason for each change available.
These are test examples, not customer case studies. Use fictional data that reflects your organisation’s complexity. Invite a future user to participate: their ability to understand and complete the process provides evidence different from a sales explanation. Record where they need help and whether the difficulty comes from configuration, terminology or the workflow itself.
Examine data, support and future growth
Identify information stored in spreadsheets, files and other applications. Ask how the initial import will work, who will correct inconsistencies and what validation results will be delivered. If the group contains several legal entities, responsibilities and records should be separated before management indicators are consolidated.
Implementation support also belongs in the decision: named contacts, training for each role, support arrangements, available materials and issue resolution procedures. Obtain written confirmation of included work and separately charged services. The Explora entry on OSH indicators helps define the underlying data and calculations your organisation needs to explain.
Consider ordinary changes as well as exceptional growth. A new location, a replacement supervisor or a different contractor should each have a clear update process. Ask who performs that change and whether it affects access, pricing or historical reports.
Choose through a test and a launch plan
Build a short comparison of criteria, evidence and assessment owners. Identify essential requirements that cannot be offset by a high score elsewhere. Keep unresolved questions visible and close them before authorising deployment.
For additional detail, explore managing the annual SG-SST work plan in software and contractor management in Colombia. When evaluating Sabentis OSH software, bring these scenarios into the discussion. They help define a proposal for your operation and an implementation with outcomes the team can verify.
A practical checklist for validating a Colombian SG-SST proposal
Prepare a decision record that distinguishes a commercial answer from a demonstrated capability. These checks complement the operational scenarios and help define how the implementation project will be accepted.
- Record the applicable minimum-standards group and who validated the combination of workforce size and risk class.
- Separate each requirement into necessary data, human activity and evidence; check which part the proposed software actually supports.
- Enter an annual-plan activity whose date changes and check that the reason remains visible when its report is produced.
- Request a sample export to confirm that your records can be interpreted without relying on screenshots of the application.
- Clarify who will review regulatory changes and translate them into procedures, responsibilities and configuration where necessary.
Frequently asked questions about selecting SG-SST software
Do the same minimum standards apply to every company?
No. Resolution 0312 distinguishes requirements by workforce size and risk class, with specific conditions that must be reviewed. Choosing a template solely by headcount is insufficient. Before configuring the system, confirm which group applies to the company’s activity and particular circumstances.
Does software replace the person responsible for the SG-SST?
No. It can support records, follow-up and information access within its contracted scope. The company still needs the people, competence and resources appropriate to its system. Automation does not take over professional assessment or turn insufficient evidence into proof of a properly completed activity.
Can a small company start with only a few processes?
Technology implementation can proceed in stages, starting with priority needs and manageable data. That sequence does not reduce applicable preventive obligations. Keep an operational procedure for processes that are not yet digitised and define when they will be incorporated into the system.
What evidence supports a claim of compliance with Resolution 0312?
Request a list of specific requirements, supported workflows and tasks retained by the organisation. Then test a complete case and examine its evidence. The answer should expose exclusions and responsibilities; a broad commercial statement does not establish effective compliance of the company’s own SG-SST.
Legislation and sources consulted
- Colombia: Decree 1072 of 2015: Chapter 2.2.4.6: organisation, documentation and monitoring of Colombia’s SG-SST.
- Colombia: Resolution 0312 of 2019: minimum standards differentiated according to company conditions; a basis for defining scope before configuring the tool.
Sources consulted on 6 October 2026. Checklists and examples are practical implementation proposals.
